It is important to understand the scope of Technology Knowledge Management, applicable to Capgemini. The first step in Transition Handover-In phase is to review the contract and the Service Governance Plan (SGP) to understand the client’s expectations pertaining to Technology Knowledge Management. Once understood, the Technology Knowledge Manager must prepare the Technology Knowledge Management Procedures to detail out the workflows for the various activities involved in Technology Knowledge Management, along with roles and responsibilities for the same. These should be created by referring to Capgemini standards and tailored using the tailoring guidelines to meet specific Client requirement. Technology Knowledge Manager must also identify tools needed to enable the Technology Knowledge Management process.

This stream focuses on the system for managing the knowledge objects related to client’s technology assets (e.g. applications, infrastructure) in scope. These knowledge objects may include known error records, technology related documents, SOPs etc. The Technology Knowledge Manager should establish rules for managing these and other SD teams will be responsible for implementing the rules. For example, the Technology Knowledge Manager establishes policies and procedures around documenting the known error records in known error database and the Problem Management is responsible for creating and modifying those known error records in alignment with the rules.

This stream works in tandem with engagement level Knowledge Management stream (USM). The USM Knowledge Management is a process internal to Capgemini and focusses on leveraging best practices across different Capgemini engagements. The Technology Knowledge Management stream, however, centers around knowledge management related to client’s technology assets (applications and infrastructure), within the scope of engagement.